Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(template): add suggest predicate template issue #785

Merged
merged 1 commit into from
Oct 15, 2024

Conversation

ccamel
Copy link
Member

@ccamel ccamel commented Oct 14, 2024

Self explanatory.

(based on #380).

Summary by CodeRabbit

  • New Features
    • Introduced a new issue template for proposing logic predicates in the Axone blockchain, enhancing clarity and completeness in submissions.

@ccamel ccamel self-assigned this Oct 14, 2024
Copy link
Contributor

coderabbitai bot commented Oct 14, 2024

Walkthrough

A new issue template named suggest_predicate.md has been added to the .github/ISSUE_TEMPLATE directory. This template is designed to guide users in proposing new logic predicates for the Axone blockchain's logic module. It includes structured sections for purpose, expected behavior, examples, acceptance criteria, and references, facilitating clear and comprehensive submissions.

Changes

File Path Change Summary
.github/ISSUE_TEMPLATE/suggest_predicate.md New issue template created for proposing logic predicates.

Poem

In the garden of logic, a new path we tread,
With templates to guide us, new predicates spread.
Prolog's embrace, in structure we find,
Clarity blooms, with each thoughtful mind.
Hop along, dear friends, let ideas take flight,
In the Axone blockchain, our futures are bright! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

codecov bot commented Oct 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #785   +/-   ##
=======================================
  Coverage   42.77%   42.77%           
=======================================
  Files         108      108           
  Lines        5078     5078           
=======================================
  Hits         2172     2172           
  Misses       2796     2796           
  Partials      110      110           

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (4)
.github/ISSUE_TEMPLATE/suggest_predicate.md (4)

6-8: Consider enhancing the Purpose section with more guidance.

While the current prompt is clear, providing more specific guidance or examples could help users articulate the purpose of their proposed predicate more effectively. This could lead to more comprehensive and useful submissions.

Consider expanding the prompt like this:

Implement a Prolog predicate to ... [briefly describe the predicate's main function]

This predicate is needed because ... [explain the use case or problem it solves]

10-20: LGTM: Well-structured Expected behavior section.

The Expected behavior section is well-organized and uses correct Prolog notation. It provides a clear structure for users to define their predicate's signature and explain its parameters.

Consider adding a brief explanation of the input/output modes ('+', '?', '-') for users who might be less familiar with Prolog conventions. For example:

Where:
- `+` denotes an input argument
- `?` denotes an input or output argument
- `-` denotes an output argument

- `A`: ...
- `B`: ...
- `C`: ...
🧰 Tools
🪛 LanguageTool

[uncategorized] ~18-~18: Loose punctuation mark.
Context: ...oo(+A, ?B, -C) is det ``` Where: - A: ... - `B`: ... - `C`: ... ## 🎯 Exampl...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~19-~19: Loose punctuation mark.
Context: ...-C) is det Where: - `A`: ... - `B`: ... - `C`: ... ## 🎯 Example prolo...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~20-~20: Loose punctuation mark.
Context: ... Where: - `A`: ... - `B`: ... - `C`: ... ## 🎯 Example prolog example :...

(UNLIKELY_OPENING_PUNCTUATION)


22-33: LGTM: Well-structured Example section with usage and expected output.

The Example section provides a clear structure for users to demonstrate both the usage of their proposed predicate and its expected output.

To make the example more comprehensive, consider adding a prompt for users to provide multiple examples, especially edge cases. For instance:

## 🎯 Examples

### Basic Usage
[existing example structure]

### Edge Case / Special Scenario
[add another example structure here]

This would encourage users to think through different scenarios and provide more thorough examples.


35-43: LGTM: Comprehensive Acceptance Criteria and References sections.

The Acceptance Criteria provide a clear checklist for ensuring the quality and completeness of the proposed predicate. The References section allows for additional context and resources.

Consider the following enhancements:

  1. In the Acceptance Criteria, add a point about performance considerations:

    - [ ] The predicate's performance has been considered and optimized if necessary
  2. In the References section, encourage users to link to similar predicates in other Prolog systems or relevant academic papers:

    ## 🔗 References and linked predicates
    
    - SWI-Prolog: ...
    - Similar predicates in other Prolog systems: ...
    - Relevant academic papers or articles: ...

These additions would promote more thorough consideration of the predicate's implementation and its place within the broader Prolog ecosystem.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 025dd8b and d5db7ad.

📒 Files selected for processing (1)
  • .github/ISSUE_TEMPLATE/suggest_predicate.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
.github/ISSUE_TEMPLATE/suggest_predicate.md

[uncategorized] ~18-~18: Loose punctuation mark.
Context: ...oo(+A, ?B, -C) is det ``` Where: - A: ... - `B`: ... - `C`: ... ## 🎯 Exampl...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~19-~19: Loose punctuation mark.
Context: ...-C) is det Where: - `A`: ... - `B`: ... - `C`: ... ## 🎯 Example prolo...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~20-~20: Loose punctuation mark.
Context: ... Where: - `A`: ... - `B`: ... - `C`: ... ## 🎯 Example prolog example :...

(UNLIKELY_OPENING_PUNCTUATION)

🔇 Additional comments (2)
.github/ISSUE_TEMPLATE/suggest_predicate.md (2)

1-4: LGTM: Well-structured metadata section.

The metadata section is correctly formatted and provides clear information about the purpose of this issue template.


1-43: Overall, this is a well-structured and comprehensive issue template.

The template provides a clear framework for users to suggest new logic predicates, covering all necessary aspects from purpose to acceptance criteria. The suggested enhancements aim to provide more guidance and encourage more thorough submissions, which should improve the quality of predicate proposals.

Great job on creating this template! It will significantly streamline the process of suggesting new predicates for the Axone blockchain's logic module.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~18-~18: Loose punctuation mark.
Context: ...oo(+A, ?B, -C) is det ``` Where: - A: ... - `B`: ... - `C`: ... ## 🎯 Exampl...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~19-~19: Loose punctuation mark.
Context: ...-C) is det Where: - `A`: ... - `B`: ... - `C`: ... ## 🎯 Example prolo...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~20-~20: Loose punctuation mark.
Context: ... Where: - `A`: ... - `B`: ... - `C`: ... ## 🎯 Example prolog example :...

(UNLIKELY_OPENING_PUNCTUATION)

Copy link
Contributor

@bdeneux bdeneux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice idea 🤩

Copy link
Member

@amimart amimart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure anyone will use it apart from us :p, but there is clearly a need to set up a framework on issues thx :)

@ccamel ccamel merged commit c05bdc3 into main Oct 15, 2024
20 checks passed
@ccamel ccamel deleted the chore/issue-template-suggest-predicate branch October 15, 2024 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants